Running a publishing job

Running a publishing job starts the job immediately. Repeating a past publishing job runs the job immediately using the current options.

Note    If the source system contains many documents, we recommend that you perform the first run of the publishing job outside of business hours. The publishing job could take a considerable amount time depending on the size of the source data.

To run a publishing job immediately:

1. In Meridian Enterprise Server Configurator, in the Data Exchange group, click Jobs. The All Jobs page appears and lists the existing publishing jobs. The jobs are grouped by the name of the computer (cluster node) to which they have been assigned.
2. Select the job that you want to run and then in the toolbar, click Run . The job is started as a background task. For information about background tasks, see Monitoring background tasks.

To repeat a past publishing job:

1. In Enterprise Server Configurator, open the Tasks page as described in Monitoring background tasks.
2. Select the job that you want to repeat and click Repeat. A confirmation dialog box appears.
3. Click YES. The job is copied to the top of the Tasks list and starts immediately.

Notes

• A publishing job will generate an error if licenses for any of its system links or rendering modules are unavailable.
• No two publishing jobs may run at the same time on the same computer. A publishing job and a synchronization job may run at the same time.
• When an synchronization job runs, it will detect new items that can be mapped to the repository that have been added to the vault configuration since the last time that the job ran. New document types, object tag types, folder types, and reference types will be automatically added to the repository configuration and mapped accordingly. New document and folder properties will stop the publishing job and show a warning that the property mappings must be updated to either include or exclude the new properties.

To schedule the publishing job to run automatically on a periodic basis, thereby keeping the repository up to date, see Scheduling a single publishing job.